Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@Makefile`:
- Around line 53-54: The Makefile's run target (run:) still executes python
main.py but init removes main.py for library templates, causing run to fail;
update the Makefile by either removing the run target entirely for library
templates or conditionally document/guard it so it only exists for application
templates—modify the run target or the init logic and the Makefile help text to
ensure run does not reference main.py when init deletes it, and mention the
change near the init and run target declarations to keep behavior consistent.

---

Nitpick comments:
In `@example_module/__init__.py`:
- Around line 2-3: The package version is duplicated: __version__ is hardcoded
in __init__.py while pyproject.toml contains the canonical version; switch to
dynamic versioning by configuring Hatch to read the package's __version__ (i.e.,
add a [tool.hatch.version] entry that points at your package to use the
__version__ symbol) so you only maintain the version in one place, or conversely
remove the duplicate from pyproject.toml and keep the single source as
__version__ in __init__.py — update the pyproject.toml Hatch config accordingly
to reference the __version__ symbol.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/actions/setup/action.yml:
- Around line 10-11: The CI step runs apt-get as a non-root user and must use
sudo; update the action.yml step that contains the two commands "apt-get update
-qq" and "apt-get install -y -qq ca-certificates curl git python3 python3-venv
libatomic1 gnupg" to prepend sudo to both invocations so the package
update/install runs with elevated privileges in GitHub-hosted runners.

In `@AGENTS.md`:
- Line 6: Update the AGENTS.md guidance that currently assumes a main.py
entrypoint: where text mentions "The entrypoint is `main.py`" (and the similar
reference later) change it to explain that `make init` may remove main.py for
library packages and that the module directory may be a library without an
entrypoint; state the default behaviors for apps versus libraries (e.g., apps
use `main.py` as entrypoint, libraries have no entrypoint and should expose
package API) and mention contributors should create a new package directory or
add an entrypoint if they need CLI/startup files.

In `@CHANGELOG.md`:
- Line 35: Replace the placeholder date in the release header "## [0.1.0] -
2024-01-XX" with a concrete ISO date (e.g., "## [0.1.0] - 2024-01-15") or remove
the date portion entirely (leaving "## [0.1.0]") if the release date is not yet
finalized; update the header text in CHANGELOG.md where the string "## [0.1.0] -
2024-01-XX" appears.

In `@POST_INIT_CHECKLIST.md`:
- Around line 24-27: The checklist's example for replacing `[[MODULE_NAME]]` is
confusing because it repeats `my_project` and omits a hyphenated project-name
example; update the example under the "Replace `[[MODULE_NAME]]` references"
bullet so it shows both forms (e.g., project name with hyphen like `my-project`
and package/module directory name like `my_project`) and clarify which form is
used where, referencing the `[[MODULE_NAME]]` placeholder text and the example
text currently showing `my_project`.

In `@README.md`:
- Line 95: Update the README line that currently reads "├── [[MODULE_NAME]]/    
# Main package (rename via make init)" to clarify that placeholder replacement
is a manual step: change the parenthetical to something like "(replace
[[MODULE_NAME]] manually as described in the init checklist)" or point to the
specific "init" checklist/section; reference the exact token [[MODULE_NAME]] and
the phrase "make init" so reviewers can find and update the README entry and any
related init instructions to avoid implying automatic renaming.

In `@TEMPLATE_GUIDE.md`:
- Around line 84-86: The guide currently tells users to run "python main.py"
after initialization but earlier sections (and later notes) indicate main.py is
removed for library-package setups, causing a dead-end; update TEMPLATE_GUIDE.md
to either remove the "python main.py" run step or make it conditional by
checking the project type (e.g., add text like "If this is an application with
an entrypoint, run `python main.py`; if you initialized a library/package (no
main.py), skip this step and follow the publishing or import instructions"), and
reference the entrypoint filename "main.py" and the
initialization/library-package notes so the doc flow remains consistent.
- Around line 117-140: Update the fenced code block that shows the project tree
in TEMPLATE_GUIDE.md to include a language specifier (use "text") after the
opening triple backticks so markdownlint MD040 is satisfied; locate the block
that begins with ``` and the directory tree (python-starter-template/ ...
TEMPLATE_GUIDE.md) and change the opening fence to ```text.
- Around line 52-53: Update the command recommendation in TEMPLATE_GUIDE.md:
replace the existing "uv sync --all-extras" suggestion with guidance to run "uv
sync" for the default dev group, or "uv sync --all-groups" (or "uv sync --group
<name>") when you need dependency groups beyond extras; ensure the doc text
around the uv sync invocation explains that --all-extras only installs extras
and will skip packages declared under [dependency-groups].

---

Outside diff comments:
In `@README.md`:
- Line 40: The README still instructs users to run "python main.py" which no
longer exists after the library initialization; update both occurrences (the
example at line ~40 and the one at ~68) to the correct runtime invocation for
this project (e.g., replace "python main.py --name World --value 42" with the
actual entrypoint such as "python -m <module_name> --name World --value 42" or
the new script name), and ensure the Quick Start example matches the package's
current entrypoint or installation instructions so first-time users can run the
app successfully.
- Line 31: Replace the incorrect use of the Poetry/uvicorn sync flag: find
occurrences of the command string "uv sync --all-extras" (used in README
examples) and change them to use the dependency-group flag for the dev group,
i.e. "uv sync --group dev"; update both occurrences (the ones noted around the
README examples) so the dev dependency group from pyproject.toml is installed
correctly.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@POST_INIT_CHECKLIST.md`:
- Line 8: Update the checklist line that currently reads "✅ Renames the module
directory from `example_module` to your project name" to clarify that package
directory names are underscore-normalized for hyphenated project names (e.g.,
"my-project" → "my_project") and make the wording consistent with the later
phrasing used elsewhere in the document (match the language that explains
hyphen-to-underscore normalization).

In `@TEMPLATE_GUIDE.md`:
- Line 43: Update the phrasing that references the package directory to say
"package directory/module name" instead of implying the directory is the exact
project name, and add an explicit hyphen-to-underscore example such as
"my-project → my_project"; reference the existing wording around
`example_module` and the sentence at lines 43 and 97 to replace the ambiguous
text and insert the `my-project` → `my_project` example for consistency.

---

Outside diff comments:
In `@README.md`:
- Line 106: Update the README entry for main.py to match the library-default
flow by annotating it as an application entrypoint that is removed for library
packages; specifically modify the line referencing "main.py" (the symbol
main.py) to read something like "main.py — application entrypoint; removed for
library packages" so it matches the other section annotations.